The Companion requests only two browser permissions: storage, for its local session state, and sidePanel, to show the Companion panel.
Its host permissions cover only linkedin.com and the approved Calder staging origin.
Within those limits, the Companion may receive the active Mission context from the approved Calder page, open the Mission's LinkedIn post when you start it, observe minimal interaction state on that exact post, keep data-minimized evidence locally, and report that state back to the Calder tab that started the Mission.
The Companion never reads or stores LinkedIn passwords, credentials or session cookies. It never clicks Like, Comment, Repost, Follow, Connect or Message on your behalf, never scans LinkedIn for unrelated activity, never harvests profiles or networks, and never implements anti-detection or evasion techniques.
It also cannot mutate your Credits or any authoritative Mission state. Verification, rewards and lifecycle changes are enforced server-side by Calder, not by the extension.
Session data stays in your browser's local extension storage and is minimized: display text is truncated, avatar links must be secure HTTPS, and profile links are format-checked. On Firefox, Mozilla's built-in data-consent model covers the declared activity permissions.
